Method, first network node, computer program and carrier for handling paging of wireless devices

ABSTRACT

A method and a first network node of a wireless network, for handling paging of a wireless device. A Radio Access Network Area, RANA, which is supported by the first network node, is registered in a database by network nodes supporting the RANA, including the first network node. The network nodes that support the RANA are then identified in the database. When it is detected that a wireless device needs to be paged in the RANA, e.g. for receiving data, a paging message is distributed to the identified set of network nodes as an instruction to perform radio transmission of the paging message. Further, which is available to the network nodes throughout the wireless network. Thereby, any network node in the wireless network, such as the first network node, is able to perform distribution of a paging message to all network nodes that support a particular RANA, as registered in the database.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/318,271 filed 16 Jan. 2019, which is a U.S. National PhaseApplication of PCT/SE2016/050725 filed 19 Jul. 2016. The entire contentsof each aforementioned application is incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to a method and a first networknode of a wireless network, for handling paging of wireless devices.

BACKGROUND

The term “wireless network” is used in this description to denote anynetwork comprising network nodes such as base stations, access points,eNodeBs or the like which are capable of radio communication withwireless devices. The term “Radio Access Network, RAN” may be usedinterchangeably throughout this disclosure instead of wireless network.The nodes in the network that performs such radio communication withwireless devices are also generally denoted “network nodes” herein. Theterm “radio access node” may be used interchangeably throughout thisdisclosure instead of network node. The wireless network or RAN mayfurther be connected to a Core Network, CN.

Further, the term “wireless device” denotes any communication equipmentthat is capable of radio communication with a wireless network, i.e.with network nodes comprised in a Radio Access Network, RAN, part of thewireless network. Some non-limiting examples of wireless devices thatmay be involved in the procedures described herein include mobilephones, smartphones, tablets, laptop computers and Machine-to-Machine.M2M, devices.

One of the main states for a wireless device in a Long Term Evolution,LTE, wireless network is the so-called idle mode, where the wirelessdevice is unknown in the RAN, although it has a context (i.e.information/data related to the wireless device) in a Core Network, CN,part of the wireless network to enable the wireless device to becontacted, e.g. for receiving data. In this idle mode or state, a listof Tracking Areas has been allocated to the wireless device by the CN.The wireless device is commonly configured to inform the CN when itenters a Tracking Area that is not in the list by sending an updatingmessage referred to as a Tracking Area Update Request to the network.This way the CN is able to keep track of where the wireless device islocated with the accuracy of the Tracking Area List. When the CN needsto contact the wireless device, e.g. when there is some data to bedelivered to the wireless device, the CN initiates paging of thewireless device in the Tracking Areas that are included in the wirelessdevice's assigned list of Tracking Areas.

When the wireless device needs to contacted and paged, the CN isresponsible for distributing a paging message to the network nodes thatsupport the Tracking Areas that are included in the wireless device'sassigned Tracking Area list. These network nodes will then transmit thepaging message at predictable, partly device specific, paging occasionsso that the wireless device is able to receive the message from at leastone of the transmitting network nodes depending on where the device islocated. To enable this procedure, each network node needs to inform theMME(s) about which Tracking Area(s) it supports, e.g. when an S1-MMEinterface is established. Hence, when a certain wireless device is to bepaged the MME can find out which network nodes a paging message shouldbe distributed to, that is according to the Tracking Area list.

This procedure is illustrated in FIG. 1 where a wireless device D1 sendstracking area updating messages to an MME or anchor node 100. e.g. atregular intervals or whenever the device D1 moves into a new TrackingArea, TA, as illustrated by an action 1:1. In another action 1:2, theMME or anchor node 100 receives data directed to the wireless device D1and finds the TA, in another action 1:3, in which the wireless device D1is presumably present according to its latest tracking area updatingmessage, in this example TA 1. The MME or anchor node 100 thendistributes a paging message to the network nodes 102 that belong to TA1, in a following action 1:4, which effectively instructs or enables thenetwork nodes 102 in TA 1 to perform radio transmission of the pagingmessage. A final action 1:5 illustrates that the paging message isaccordingly transmitted from the network nodes 102 in TA 1.

It is likely that future wireless networks, e.g. networks configuredaccording to the fifth Generation, 5G, will employ a RAN state similarto the above described non-connected idle mode in view of the wirelessdevice, but in which the wireless device is connected in view of the CN,hence the CN does not view the wireless device as idle. In this mode orstate, the RAN handles the paging and receives area updates from thewireless device. Such a state is also likely to be introduced in LTE aswell, in order to facilitate tight integration of LTE and 5G networks.This state may also be referred to as “dormant state” and in thisdescription an area assigned to the wireless device e.g. for pagingpurposes is referred to as a “RAN Area, RANA”. The dormant state may beused instead of the idle mode in 5G or it may exist in parallel with theidle mode, such that the dormant state and the idle mode may complementeach other.

In the dormant state there will be an anchor node, which could be one ofthe network nodes in the RAN, that maintains the wireless device'sassociated connection(s) with the CN, such as any control and user planeS1 connections. This anchor node will also be responsible for initiatingand distributing paging messages among the network nodes which thewireless devices may listen to in their current RANA when in the dormantstate.

Since the RAN handles the paging procedures in such networks, it needsto keep track of which network nodes belong to the same RANA. This isneeded for enabling paging in relevant areas and may also be useful forretrieval of device context during page response and network accessinitiated by the wireless device when in the dormant state. The term“context” here refers to information/data related to the wirelessdevice, wherein this information/data may be static and/or dynamic,where information related to the capabilities or subscription associatedwith the wireless device could be examples of the former and establishedbearers, recent mobility statistics and last known location could beexamples of the latter. Throughout this description, a network nodesupporting a RANA means that the network node belongs to the RANA. Eachnetwork node should thus preferably be aware of all the other networknodes that belong to the same RANA and optionally also have a connection(e.g. an X2 interface or a corresponding interface) to all the othernetwork nodes in the same RANA to facilitate page distribution.

However, this may be difficult or impossible as compared to the idlestate paging in LTE, where the node initiating the paging, i.e. the MME,already has knowledge and the necessary interfaces to all the networknodes that should be involved in the paging. Moreover, the set ofnetwork nodes belonging to a RANA may change over time, such as whennetwork nodes are added, removed, relocated or reconfigured. It is thusa problem that a paging message may not be transmitted from one or morenetwork nodes in a paged RANA because of inadequate knowledge aboutwhich network nodes currently belong to the RANA.

SUMMARY

It is an object of embodiments described herein to address at least someof the problems and issues outlined above. It is possible to achievethis object and others by using a method and a first network node asdefined in the attached independent claims.

According to one aspect, a method is performed by a first network nodeof a wireless network, for handling paging of a wireless device. In hismethod, the first network node registers in a database, a Radio AccessNetwork Area. RANA, which is supported by the first network node. Thefirst network node further identifies in the database a set of networknodes that support the RANA. When detecting that a wireless device needsto be paged in the RANA, the first network node distributes a pagingmessage to the identified set of network nodes as an instruction toperform radio transmission of the paging message.

According to another aspect, a first network node of a wireless networkis arranged to handle paging of a wireless device. The first networknode is configured. e.g. by means of a registering unit, to register ina database, a Radio Access Network Area, RANA, which is supported by thefirst network node. The first network node is also configured. e.g. bymeans of an identifying unit, to identify in the database a set ofnetwork nodes that support the RANA. The first network node is furtherconfigured, e.g. by means of a detecting unit and a distributing unit,respectively, to detect that a wireless device needs to be paged in theRANA, and to distribute a paging message to the identified set ofnetwork nodes as an instruction to perform radio transmission of thepaging message.

It is an advantage of the above method and first network node that thepaging message can be distributed by the network node itself in anefficient manner without using any central paging distribution node.Another advantage is that when essentially all network nodes of the RANAhave registered their RANA support in the database in this way, anynetwork node in the RANA can look up the database and identify thenetwork nodes of the RANA with great accuracy and reliability anddistribute the paging message to the identified network nodes across theentire RANA.

The above method and first network node may be configured andimplemented according to different optional embodiments to accomplishfurther features and benefits, to be described below.

BRIEF DESCRIPTION OF THE DRAWINGS

The solution will now be described in more detail by means of exemplaryembodiments and with reference to the accompanying drawings, in which:

FIG. 1 is a communication scenario illustrating a conventional procedurefor paging a wireless device, according to the prior art.

FIG. 2 is a communication scenario illustrating an example of how thesolution may be employed for handling paging of a wireless device,according to some possible embodiments.

FIG. 3 is a flow chart illustrating a procedure in a first network node,according to further possible embodiments.

FIG. 4 is an example information table in a database comprisingregistered RANAs as supported by different network nodes, in accordancewith embodiments herein.

FIG. 5 is a communication scenario illustrating another example of howthe solution may be employed, according to further possible embodiments.

FIG. 6 is a communication scenario illustrating another example of how apaging message is distributed in at least two successive hops, accordingto further possible embodiments.

FIG. 7 is a communication scenario illustrating another example of how adevice context can be retrieved from a network node of another RANA,according to further possible embodiments.

FIG. 8 is a flow chart illustrating another example of a procedure inthe first network node, according to further possible embodiments.

FIG. 9 is a block diagram illustrating a first network node in moredetail, according to further possible embodiments.

DETAILED DESCRIPTION

Briefly described, a solution is provided to enable efficient andcorrect distribution of a paging message to be transmitted over radiofrom network nodes of at least one RANA in a wireless network. Inparticular, the solution may be used to ensure that the paging messagecan be distributed to all network nodes that currently belong to andsupport a particular RANA, even when there is no central nodecorresponding to the above-described MME which has RANA information thatis up-to-date and distributes paging messages. This can be accomplishedby registering information in a database about which network nodessupport the RANA, and any network node in the wireless network can thenretrieve RANA information from the database to identify which networknodes a paging message should be distributed to whenever paging isperformed across a RANA.

This registration is done by the network nodes themselves. e.g. when therespective network node is added, i.e. deployed in the RAN which mayhappen when the network node is established and connected to thewireless network. A registration may also be made when a previously maderegistration needs to be updated for the network node, such as when thenetwork node switches from one RANA to a new one (e.g. because theoperation and maintenance system determined that it would be beneficialto move a RANA border). A RANA may thus be reconfigured from time totime by adding or removing network nodes. The network node may alsoconfirm to the database that a previously made RANA registration remainsvalid, e.g. at regular intervals.

It is an advantage of this solution that distribution of a pagingmessage can be made locally by the network nodes themselves in anefficient manner, without using any central paging distribution nodesuch as the MME which may not be implemented in some types of networkssuch as 5G and evolved LTE networks. Another advantage is that thesolution ensures that all network nodes that support a particular RANAcan be identified with great accuracy and reliability by means of theregistered information in the database which can be kept up-to-date.Thereby, any network node in the RANA is able to distribute the pagingmessage to all other network nodes that support the RANA, based on theinformation registered in the database.

In the RANA registration, each network node identifies itself and thesupported RANA, e.g. by entering a network node identity and a RANAidentity in the database. The network node may also register a currentlyused network address of the network node such as an IP address or aFully Qualifier Domain Name, FQDN, that can be resolved into an IPaddress via the Domain Name System, DNS. The database may be implementedas a specific storage entity that is dedicated for the purpose ofholding RANA information. The database could also be realized as adynamic DNS node which is capable of resolving identities into IPaddresses.

An example of how the solution may be employed for handling paging of awireless device, will now be described with reference to a communicationscenario illustrated in FIG. 2 . In this scenario, a wireless networkcomprises multiple RANAs denoted RANA 1, RANA 2, RANA 3, . . . whereRANA N is one of the RANAs in the network. Each RANA is supported by aset of network nodes in the sense that when a paging message is to betransmitted across a particular RANA in order to reach a paged wirelessdevice, each network node that supports that RANA needs to transmit thepaging message so that the wireless device has a chance to receive thepaging message regardless of where it is located within the RANA. If thewireless device is not in the RANA, the paging message may need to bedistributed across a larger area including one or more other RANAs,which is however not illustrated in this figure.

In FIG. 2 , it is illustrated that various network nodes in the RANAs,including a first network node 200 that supports RANA N, registersinformation in a database 202 regarding which RANAs they currentlysupport, as schematically indicated by an action 2:1. This activitynaturally involves several individual registrations made by the networknodes at different independent occasions. e.g. when being deployed inthe RANA or reconfigured such that its RANA support is affected, or whenjust prolonging a previous registration. For example, a network node maysupport more than one RANA at the same time, which means that twoadjacent RANAs are supported by different parts of the network node'scoverage area, e.g. different cells or different sectors, or the twoRANAs may have partly overlapping coverage in an area served by such anetwork node. Action 2:1 may thus be performed at any time “in thebackground”, e.g. on a regular or continuous basis or whenever a changehas occurred.

A next action 2:2 illustrates that the first network node 200 of RANA Nqueries the database 202 to identify the network nodes supporting, i.e.belonging to, its own RANA N. This query may comprise an identifier ofRANA N, e.g. in the form of an FQDN or a type of identifier used onlyfor RANAs, which can be used as a lookup key in the database which thenreturns a list of network nodes that support the queried RANA N. In thislist, the network nodes may be identified by their IP addresses or byrespective FQDNs which can be translated into IP addresses. In general,an IP address can be seen as contact information useful for establishingconnections with the network nodes.

If the network nodes have performed their RANA registrations properly asof action 2:1, this list should be accurate by including all networknodes that support RANA N. The first network node 200 may repeat thisaction, e.g. at regular intervals, to make sure it has RANA informationthat is always up-to-date. Once the list of network nodes is obtained,the first network node 200 may also establish a connection with eachnetwork node in the list using their respective IP addresses. Thereby,the first network node 200 is prepared to distribute any paging messagesacross its own RANA N.

Another action 2:3 illustrates that the first network node 200 receivesdata e.g. from a core network, not shown, which data is addressed to awireless device D1 which has been detected as being likely locatedsomewhere in RANA N. The expected whereabouts of wireless devices in thewireless network may be generally maintained based on tracking areaupdating messages from the wireless device in the manner describedabove, e.g. by suitable functionality in the core network. In thissolution it is simply assumed that such location information isavailable with the accuracy level of a RANA, and the currently presumedRANA of D1, in this case RANA N, may be indicated to the first networknode 200 in a suitable manner.

Having received the data to be transmitted to the wireless device D1,the first network node 200 is responsible for finding a network nodefrom which the device D1 can properly receive radio signals and detect apaging message directed to D1, for establishing a session where the datacan be transmitted to D1. At this point, the network node 200 thereforeneeds to know virtually all network nodes that currently support theRANA N and distribute the paging message to these network nodes forradio transmission over their respective coverage areas. This ispossible as action 2:2 has been performed, and the list of network nodesobtained in that action can now be utilized for finding the networknodes to which the paging massage should be distributed. Alternatively,or additionally, action 2:2 may be performed upon receiving the data,that is after action 2:3.

A final action 2:4 illustrates that the first network node 200distributes the paging message to the network nodes in the list, so thatthey can page D1 by transmitting the paging message over radio to see ifany of the network nodes receives any response from the device D1. If anetwork node in RANA N receives a page response from D, that networknode will fetch the data from the first network node 200 and transmitthe data to device D1 in a communication session. The paging procedureas such may be conducted in a conventional manner which is outside thescope of this disclosure.

An example of how the solution may be employed in terms of actionsperformed by a first network node, such as the network node 200 of FIG.2 , for handling paging of a wireless device, will now be described withreference to the flow chart in FIG. 3 . Reference will also be made,without limiting or losing applicability of the features described, toelements in the example shown in FIG. 2 . In this procedure it isassumed that the first network node 202 is capable of distributing apaging message to other network nodes whenever a wireless device is tobe paged. Although this example refers to paging in one RANA, it can beunderstood that the example is also applicable for paging in two or moreRANAs in the manner described below.

The procedure illustrated by FIG. 3 can thus be used to accomplish thefunctionality and benefits described above. In this description, theterm “Radio Access Network Area. RANA” should be understood as an areacomprised of cells or similar coverage areas which are served by networknodes supporting the RANA so that a wireless device can be paged in theRANA by radio transmission of a paging message from the network nodes ofthe RANA. “Tracking area” and “Paging area” are examples of alternativeterms that could also be used herein.

The actions of FIG. 3 will first be briefly outlined and then someexample embodiments that could optionally be employed will also bedescribed and explained. A first action 300 illustrates that the firstnetwork node 200 registers in a database 202, a RANA which is supportedby the first network node 200. This action corresponds to action 2:1 inFIG. 2 . It could also be said that the network node 200 “belongs” tothis RANA by supporting it. In this action 300, “a RANA” is not limitedto only a single RANA but it should be seen as at least one RANA thusnot excluding registration of two or more supported RANAs whenapplicable. In this registration operation, the first network node 200may obtain from the database 202 information about other network nodesalso supporting the same RANA.

In a next action 302, the first network node 200 identifies in thedatabase 202 a set of network nodes 204 that support the RANA to whichthe first network node 200 belongs, i.e. its own RANA. This informationcan be regarded as reliable and valid provided that all network nodes204 have registered their RANA support.

FIG. 4 is a table illustrating an example of information that has beenregistered in a database in the above-described manner. It is thus shownthat a first set of network nodes 11, 12, 13, . . . support RANA 1, asecond set of network nodes 21, 22, 23, . . . support RANA 2, a thirdset of network nodes 31, 32, 33, . . . support RANA 3, and so forth. Theinformation registered for each network node, schematically illustratedas “Node xx”, includes a network node identifier and some suitablecontact information that can be used for establishing a connection tothe respective node.

A next optional action 304 illustrates that the first network node 200may at this point establish connections to the network nodes inidentified set of network nodes 204 supporting the RANA, e.g. by usingcontact information of the network nodes registered in the database. Ina further action 306, the first network node 200 detects that a wirelessdevice D1 needs to be paged in the above-mentioned RANA. This could bemade when receiving data to be transmitted to the device D1 as of action2:3 in FIG. 2 . As indicated above, connections may optionally beestablished to the network nodes after detecting that device D1 needs tobe paged so that action 304 would be performed after action 306. In thisaction, it is also possible to detect that the device D1 needs to bepaged in one or more other RANAs as well. For example, the device D1 mayfirst be paged in one RANA and if it is not found in that RANA, thepaging may be expanded across one or more other RANAs.

A final action 308 illustrates that the first network node 200distributes a paging message to the identified set of network nodes 204as an instruction to perform radio transmission of the paging message.If not done earlier, as of action 304, the first network node 200 willin action 308 make sure that a connection is established to each networknode in the set of network nodes 204 to enable distribution of thepaging message. The paging message may also be sent to a network nodevia an intermediate network node so that the paging message can bedistributed in multiple “hops”. An example of such distribution will bedescribed later below with reference to FIG. 6 .

Some non-limiting example embodiments that can be used in the aboveprocedure, will now be described. In one example embodiment, the firstnetwork node 200 may establish connections to at least some of thenetwork nodes in the identified set of network nodes 204, and can thendistribute the paging message using said connections, e.g. as describedabove for action 304. The first network node 200 may further establishconnections to one or more network nodes supporting other RANAs as well.

In another example embodiment, the first network node 200 may performsaid registering and identifying via a core network node serving theRANA. If so, another example embodiment may be that the action ofdistributing may comprise sending the paging message to a core networknode as a relay for distribution of the paging message to the identifiedset of network nodes. These embodiments may be useful when the currentRANA does not have connections towards other RANAs.

In another example embodiment, the paging message sent to the corenetwork node may be addressed to the RANA or to each network node in theidentified set of network nodes 204. In either case, the core networknode is able to contact all network nodes of the RANA and relay thepaging message thereto. In another example embodiment, the core networknode may also be used as a relay for retrieving a context of thewireless device from another network node belonging to the RANA.

The context retrieval may in exemplary embodiments be enabled by acontext identifier, which includes an identifier of a network nodestoring the context and preferably also a part identifying the contextwithin the network node storing the context. The context identifier maybe provided from the wireless device when it contacts the network, e.g.when responding to a page or when switching from a dormant to an activestate. In the case of paging, an alternative could also be that thecontext identifier is included in the paging message which in turn isdistributed from the anchor node to network nodes taking part in thepaging of the wireless device.

An example of how a core network node may be employed in theabove-described embodiments is shown in FIG. 5 where the first networknode 200 is connected to the core network node 500 which is configuredto convey RANA registrations from network nodes of a RANA N in thedatabase 202, and to assist distribution of paging messages to thenetwork nodes of RANA N. A first action 5:1 illustrates that the firstnetwork node 200 performs a RANA registration of RANA N which issupported by network node 200, via the core network node 500. Althoughnot shown here, it is assumed that the other network nodes of RANA Nalso perform RANA registrations so that the database 202 is populatedwith RANA information in the manner described above, e.g. as shown inFIG. 4 .

In another action 5:2, the first network node 200 identifies in thedatabase 202 a set of network nodes 204 that support the RANA N, whichis done by sending a database query or the like to the database 202 viathe core network node 500. In another action 5:3, the first network node200 sends a paging message to core network node 500 for distribution tothe network nodes 204 of RANA N. The core network node 500 then relaysthe paging message to all network nodes 204 of RANA N, in action 5:4.

It was mentioned above that a network node may support and belong tomore than one RANA at the same time. In another example embodiment, thefirst network node 200 may in that case register in the database 202multiple RANAs which are supported by the first network node 200. Thefirst network node 200 may then detect that the wireless device needs tobe paged in at least one of the registered RANAs. In that case the firstnetwork node 200 is able to distribute the paging message across the atleast one RANA using the information in the database.

In another example embodiment, the registering performed in action 300may comprise registering in the database 202 an IP address or a FullyQualified Domain Name, FQDN, of the first network node 200 and anidentifier of the RANA supported by the first network node 200. Inanother example embodiment, said registering of action 300 may beperformed when the first network node 200 is deployed in the RANA orwhen the first network node 200 has been reconfigured so that apreviously made registration needs to be updated. In another exampleembodiment, the identifying performed in action 302 may comprise sendinga query to the database 202 with an identifier of the RANA as a lookupkey, which was also mentioned above.

In another example embodiment, the paging message may be received fromanother network node belonging to the RANA and the first network node200 may in that case act as a hub node, a relaying node or a forwardingnode by forwarding the paging message over connections to at least someof the network nodes that belong to the RANA.

In another example embodiment, the first network node 200 may send thepaging message in a first hop only to a subset of neighbouring networknodes in the identified set of network nodes, so that the paging messageis distributed across the identified set of network nodes by means of atleast a second hop of forwarding the paging message from theneighbouring network nodes to their respective neighbouring networknodes belonging to the same RANA.

An example of how this embodiment may be employed is shown in FIG. 6where the first network node 200 sends the paging message to threeneighbouring network nodes, indicated as a first hop. Having receivedthe paging message, each of those three neighbouring network nodesforwards the paging message to their respective neighbouring networknodes, indicated as a second hop. In this embodiment, the paging messagemay be sent to any number of neighbouring network nodes and any numberof hops may be required before the message has reached all network nodesof the RANA, depending on the size and configuration of the network. Theembodiment is thus not limited in this respect.

In another example embodiment, when multiple hops are employed, thepaging message may comprise a message identifier which can be used toavoid that the paging message is forwarded to any network node fromwhich the same paging message has been received. For example, thenetwork nodes that received the paging message in the first hop canthereby avoid sending the paging message in the second hop back to thenetwork node that sent the message in the first hop. In another exampleembodiment, the first network node 200 may also establish connections tothe above-mentioned subset of neighbouring network nodes and can thensend the paging message using said connections in the first hop.

In another example embodiment, the first network node 200 may identifyin the database 202 a second network node belonging to another RANA, andretrieve from the second network node a context of the wireless devicewhen the wireless device is handed over from the second network node tothe first network node 200. FIG. 7 illustrates an example of how thefirst network node 200 may retrieve a device context by using RANAinformation that has been registered in the database 202.

In this example it is assumed that a handover procedure has beeninitiated for handing over a wireless device D1 from the second networknode 700 to the first network node 200. In a first action 7:1, the firstnetwork node 200 belonging to RANA 1 identifies the second network node700 which belongs to and supports RANA 2. The first network node 200 inthis action also establishes a connection with the network node 700using contact information that the network node 700 has registered inthe database 202 along with its RANA information. A next action 7:2illustrates that the first network node 200 retrieves a context ofdevice D1 from the identified second network node 700, which context isused by the first network node 200 for communication with the device D1after the handover has been completed. The retrieval and use of a devicecontext as such can be done in a regular manner which is however outsidethe scope of this disclosure.

Another example of how a network node of a wireless network, such as theabove first network node 200, may operate when the solution is employed,will now be described with reference to the flow chart in FIG. 8 In thisexample it is assumed that the above RANA registration in the databasehas been performed by network nodes throughout the wireless network,e.g. as described for actions 2:1 and 300. A first action 800illustrates that the network node receives a paging request from a corenetwork, thus requesting the network node to distribute a paging messageaddressed to a wireless device. This action basically corresponds toaction 2:3 in FIG. 2 .

In a next action 802, the network node determines, i.e. identifies, aRANA in which the paging message should be transmitted by network nodesin the RANA. It is then checked in a next action 804 whether thedetermined RANA is the network node's own supported RANA or not. If so,the network node identifies in the database a set of network nodes thatsupport its own RANA, in another action 806. If the determined RANA isanother RANA not supported by the network node, the network nodeidentifies in the database a set of network nodes that support the otherRANA, in another action 808. Regardless of whether action 806 or action808 was performed, a final action 810 illustrates that the network nodedistributes the paging message to the set of network nodes identified ineither action 806 or action 808 depending on the outcome of action 804.

The block diagram in FIG. 9 illustrates a detailed but non-limitingexample of how a first network node 900 of a wireless network may bestructured to bring about the above-described solution and embodimentsthereof.

The first network node 900 may thus be configured to operate accordingto any of the above-described examples and embodiments. The firstnetwork node 900 is shown to comprise a processor P and a memory M, thememory M comprising instructions executable by said processor P wherebythe first network node 900 is operative as described herein. The firstnetwork node 900 also comprises a communication unit C representingsuitable equipment for receiving and sending information in the mannerdescribed herein. The communication unit C is configured forcommunication with network nodes of the wireless network over suitableinterfaces such as the X2 interface, and using a suitable protocol forthe described communication depending on the implementation. Thesolution and embodiments herein are thus not limited to using anyspecific types of networks, technology or protocols for communication.

The first network node 900 comprises means configured or arranged toperform at least some of the actions of the flow charts in FIGS. 3 and 8. The first network node 900 is arranged to handle paging of a wirelessdevice. The first network node 900 is configured to register in adatabase 902, a Radio Access Network Area, RANA, which is supported bythe first network node 900. This operation may be performed by aregistering unit 900A in the first network node 900, e.g. in the mannerdescribed for action 300 above.

The first network node 900 is also configured to identify in thedatabase 902 a set of network nodes 904 that support the RANA. Thisoperation may be performed by an identifying unit 900B in the firstnetwork node 900, e.g. in the manner described for action 302 above. Thefirst network node 900 is further configured to detect that a wirelessdevice needs to be paged in the RANA. This operation may be performed bya detecting unit 900C in the first network node 900. e.g. in the mannerdescribed for action 306 above.

The first network node 900 is further configured to distribute a pagingmessage to the identified set of network nodes 904 as an instruction toperform radio transmission of the paging message. This operation may beperformed by a distributing unit 900D in the first network node 900,e.g. in the manner described for action 308 above.

It should be noted that FIG. 9 illustrates various functional units inthe first network node 900, and the skilled person is able to implementthese functional units in practice using suitable software and hardware.Thus, the solution is generally not limited to the shown structures ofthe first network node 900, and the functional units 900A-D therein maybe configured to operate according to any of the features andembodiments described in this disclosure, where appropriate.

The functional units 900A-D described above could be implemented in thefirst network node 900 by means of suitable hardware and program modulesof a computer program comprising code means which, when run by theprocessor P causes the first network node 900 to perform at least someof the above-described actions and procedures. The processor P maycomprise a single Central Processing Unit (CPU), or could comprise twoor more processing units. For example, the processor P may include ageneral purpose microprocessor, an instruction set processor and/orrelated chips sets and/or a special purpose microprocessor such as anApplication Specific Integrated Circuit (ASIC). The processor P may alsocomprise a storage for caching purposes.

Each computer program may be carried by a computer program product inthe first network node 900 in the form of a memory having a computerreadable medium and being connected to the processor P. The computerprogram product or memory in the first network node 900 may thuscomprise a computer readable medium on which the computer program isstored e.g. in the form of computer program modules or the like. Forexample, the memory may be a flash memory, a Random-Access Memory (RAM),a Read-Only Memory (ROM), an Electrically Erasable Programmable ROM(EEPROM) or hard drive storage (HDD), and the program modules could inalternative embodiments be distributed on different computer programproducts in the form of memories within the first network node 900.

The solution described herein may thus be implemented in the firstnetwork node 900 by means of a computer program comprising instructionswhich, when executed on at least one processor, cause the at least oneprocessor to carry out the actions according to any of the abovefeatures and embodiments, where appropriate. A suitable carriercontaining the above computer program may also be used when implementingthe solution, wherein the carrier is one of an electronic signal,optical signal, radio signal, a computer program storage product, or acomputer readable storage medium.

Advantages of the above-described solution and its embodiments includethat distribution of a paging message can be handled internally within aRANA without using any central paging distribution node such as the MME.Further, all network nodes that support a particular RANA can beidentified with great accuracy and reliability by means of theregistered information in the database which is available to the networknodes throughout the wireless network. Thereby, any network node in thewireless network is able to perform distribution of a paging message inthe manner described above.

Some further examples and features of the above-described solution andits embodiments will now be discussed.

If a network node has been subjected to a configuration change thatimpacts the registered information in the database, it should update theinformation in the database. The network node may also inform the othernetwork nodes in the RANA which could potentially be affected by theconfiguration change. Similarly, if a new network node is deployed, itshould register its RANA and contact information in the database, andidentify all the other network nodes that have registered the same RANAin the database. The new network node may further establishconnections/interfaces to these network nodes of the RANA. Optionally, anetwork node may periodically check for relevant updates in thedatabase, e.g. as a backup solution for any changes of network nodeconfigurations that the network node may have failed to receive.

It was mentioned above that the database may be realized in a DNS node.In this case, the network nodes of a RANA could register their RANA IDas an FQDN, possibly in addition to registering a respective networknode ID as an FQDN, and a query on the RANA ID FQDN to the DNS nodewould return a list of the IP addresses registered with that RANA IDFQDN. Alternatively, the query on the RANA ID FQDN could return a listof the network node ID FQDNs of the network nodes which have registeredthis RANA ID FQDN and these network node ID FQDNs could in turn betranslated into IP addresses.

It was also mentioned above that a device context may be retrieved byusing RANA information that has been registered in the database 202. Theabove-described database mechanism could thus be used to enable anetwork node of a RANA to fetch a network internal context of a wirelessdevice from another network node outside the RANA, which was describedabove with reference to FIG. 7 . This can be done by means of“on-demand” lookup operations in the database. The actual contextfetching could use an existing connection/interface to the other networknode if such an interface/connection exists. Otherwise, a temporaryconnection/interface may be established to the other network node or thecore network node may be used as a “relay node” to convey the messagesinvolved.

This context fetching may utilize the network node ID to find thenetwork node holding the context, regardless of whether the contextfetching is relayed via a core network node or handled internally in theRAN. To support this context fetching, the network node ID should beregistered in the database 202. In case the context fetching isperformed internally within the wireless network, the network node IDcould be registered in the database as an FQDN, which may be translatedinto an IP address via DNS, or it could be associated with an IP addressin the database.

It was also mentioned above that the solution may be used to supportpaging distribution across multiple RANAs for wireless devices that areconfigured with lists of RANAs or RANA IDs, which is similar to wirelessdevices that are configured with lists of Tracking Area Identifiers inan LTE network. To this end, instead of just querying the database usingits own RANA ID, a network node may do the same also for RANA IDs ofother reasonably close RANAs, e.g. of neighboring RANAs and possiblyalso of the neighbors' neighboring RANAs. To be precise, the networknode could do this for all other RANAs that the network node may includein a list of RANAs, or RANA IDs, that it allocates to a wireless device.

It was mentioned above that the first network node 200 may receive apaging message from another network node belonging to the same RANA, andact as a hub node by forwarding the paging message over connections tothe network nodes that belong to the RANA. Some further details andfeatures of this embodiment will now be described. In this embodiment,instead of employing a full or partial “mesh” of connections betweenvirtually all network nodes, a hierarchical structure may be used whereone network node in each RANA is configured to act as a hub for theRANA. This means that the hub node has interfaces/connections to allother network nodes in the RANA and can thereby relay paging messagesbetween any network nodes in the RANA. The other network nodes may alsoestablish direct interfaces/connections to other network nodes, e.g. toneighboring network nodes having radio coverage areas adjacent to itsown radio coverage area, such that handovers of devices between thenetwork nodes may commonly occur. The hub node may in some cases forwardthe paging message to only a subset of the network nodes that belong tothe RANA. e.g. when the paging message is distributed in multiple hopsas described above for FIG. 6 .

Each hub node should register its RANA information in the database, bystoring their respective contact information and supported RANA. Anetwork node may then look up and retrieve the contact information ofthe hub node serving its RANA from the database. e.g. by including theRANA ID in a query to the database, and establish aninterface/connection to the hub node. Distribution of a paging messageto the network node of a RANA would in this case be performed via thehub node, such as when a network node that initiates paging of awireless device in the RANA sends the paging message to the hub node.Then the hub node will forward or relay the paging message to all theother network nodes in the RANA.

A paging message may also be sent to a single other network node via thehub node by addressing the paging message to the destination networknode using its network node ID.

When a paging message is distributed across multiple RANAs and/or adevice context is retrieved across RANA borders, each hub node in theRANAs is able to retrieve the contact information of all other hub nodesin the wireless network from the database, and the hub nodes canestablish interfaces/connections between each other, thus forming a fullor partial mesh. A special query for the hub nodes may be sent to thedatabase which then returns the information, including the contactinformation, that has been registered by all other hub nodes in thedatabase. For example, such a database query could be realized by usinga “wild card” RANA ID in the query that a network node would use toretrieve information about the hub node of its RANA.

Another possibility is that a hub node could be dedicated for operationas a hub node although it may also operate as a regular network node inparallel.

While the solution has been described with reference to specificexemplifying embodiments, the description is generally only intended toillustrate the inventive concept and should not be taken as limiting thescope of the solution. For example, the terms “network node”, “wirelessdevice”. “paging message”, “Radio Access Network Area. RANA”, “corenetwork node” and “hub node” have been used throughout this disclosure,although any other corresponding entities, functions, and/or parameterscould also be used having the features and characteristics describedhere. The solution is defined by the appended claims.

What is claimed is:
 1. A method performed by a radio access node of aRadio Access Network (RAN), the method comprising: receiving data from aCore Network (CN) for a wireless terminal that is in a dormant statewith respect to the RAN but for which the radio access node maintainscontrol and user plane connections to the CN; determining a RAN Area(RANA) to which the radio access node belongs; identifying other radioaccess nodes that belong to the RANA; and initiating paging of thewireless terminal in response to receiving the data from the CN, thepaging initiated by the radio access node for the other radio accessnodes.
 2. The method of claim 1, wherein initiating the paging comprisessending a paging message to a node in the CN, for relaying towards theother radio access nodes that belong to the RANA.
 3. The method of claim2, wherein the paging message is addressed to the RANA.
 4. The method ofclaim 2, wherein the paging message is addressed to the other radioaccess nodes that belong to the RANA.
 5. The method of claim 1, whereininitiating the paging comprises sending a paging message only to asubset of the other radio access nodes in the RANA, for furtherforwarding by the subset of other radio access nodes within the RAN, thesubset being first-hop neighbors of the radio access node.
 6. The methodof claim 5, further comprising including an identifier in the pagingmessage, to prevent forwarding of the paging message within the RAN toany radio access node from which the same paging message has beenreceived.
 7. The method of claim 1, further comprising registering theradio access node in a database as belonging to the RANA, so thatanother radio access node can use the database to determine that theradio access node belongs to the RANA.
 8. The method of claim 1, whereinthe identifying the other radio access nodes that belong to the RANAincludes: accessing a database that holds registrations for radio accessnodes that belong to the RANA.
 9. A radio access node configured foroperation in a Radio Access Network (RAN), the radio access nodecomprising: a processor and a memory, the memory storing instructionsexecutable by the processor whereby the radio access node is configuredto: receive data from a Core Network (CN) for a wireless terminal thatis in a dormant state with respect to the RAN but for which the radioaccess node maintains control and user plane connections to the CN;determine a RAN Area (RANA) to which the radio access node belongs;identify other radio access nodes that belong to the RANA; and initiatepaging of the wireless terminal in response to receiving the data fromthe CN, the paging initiated by the radio access node for the otherradio access nodes.
 10. The radio access node of claim 9, wherein, toinitiate the paging, the radio access node is configured to send apaging message to a node in the CN, for relaying towards the other radioaccess nodes that belong to the RANA.
 11. The radio access node of claim10, wherein the paging message is addressed to the RANA.
 12. The radioaccess node of claim 10, wherein the paging message is addressed to theother radio access nodes that belong to the RANA.
 13. The radio accessnode of claim 9, wherein, to initiate the paging, the radio access nodeis configured to send a paging message only to a subset of the otherradio access nodes in the RANA, for further forwarding by the subset ofother radio access nodes within the RAN, the subset being first-hopneighbors of the radio access node.
 14. The radio access node of claim13, wherein the radio access is configured to include an identifier inthe paging message, to prevent forwarding of the paging message withinthe RAN to any radio access node from which the same paging message hasbeen received.
 15. The radio access node of claim 9, wherein the radioaccess node is further configured to register the radio access node in adatabase as belonging to the RANA, so that another radio access node canuse the database to determine that the radio access node belongs to theRANA.
 16. The radio access node of claim 9, wherein the radio accessnode is further configured to identify the other radio access nodes thatbelong to the RANA by accessing a database that holds registrations forradio access nodes that belong to the RANA.